File update system and boot management system of mobile communication terminal, method of updating file in mobile communication terminal, and method of booting mobile communication terminal

ABSTRACT

Disclosed are a file update system of a mobile communication terminal which is capable of recovering Same Owner ID Error caused by damage of a file header in an EFS (Embedded File System) area of the mobile communication terminal, a boot management system of a mobile communication terminal which is capable of preventing a fatal error caused by damage of a file header in an EFS area of the mobile communication terminal, a method of updating a file in the mobile communication terminal, and a method of booting the mobile communication terminal which is capable of preventing a fatal error caused by damage of a file header in an EFS area of the mobile communication terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a divisional of U.S. patent application Ser. No.11/258,294, filed Oct. 25, 2005, which claims the priority of KoreanPatent Application No. 2005-00536, filed on Jan. 4, 2005, in the KoreanIntellectual Property Office, the disclosures of which are incorporatedherein in their entirety by reference.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to a mobile communication terminal and,more particularly, to a file update system of a mobile communicationterminal which may recover Same Owner ID Error caused by damage of afile header in an Embedded File System (EFS) area of the mobilecommunication terminal, a boot management system of a mobilecommunication terminal which may prevent a fatal error caused by damageof a file header in an EFS area of the mobile communication terminal, amethod of updating a file in the mobile communication terminal, and amethod of booting the mobile communication terminal which may prevent afatal error caused by damage of a file header in an EFS area of themobile communication terminal.

2. Description of Related Art

In general, when a file stored in a part of an EFS area of a mobilecommunication terminal is updated, e.g., modified or relocated, theupdated file is not overwritten in the part of the EFS area but isstored in another part of the EFS area. As a result, the updated filecoexists in the EFS area together with the file prior to updating.

Meanwhile, each file stored in the EFS area has its own ID which is usedto identify each file. An updated file includes a different file namefrom that of an existing file prior to updating in its header butincludes the same ID information as that of the existing file in itsheader.

If a header of a file block is damaged due to physical or electricalfactors while a mobile communication terminal is managing data usingEFS, a phenomenon called Same Owner ID Error occurs.

In more detail, the Same Owner ID Error occurs in a case where there arefile blocks having the same ID but different file names. In this case,when a mobile communication terminal is powered on, a fatal error occursduring performing a process of initializing EFS in a booting process ofthe mobile communication terminal. As a result, the mobile communicationterminal is automatically power-reset and thus becomes irrecoverable.

SUMMARY

An embodiment of the present invention provides a file update system ofa mobile communication terminal which may recover Same Owner ID Errorcaused by damage of a file header in an EFS (Embedded File System) areaof the mobile communication terminal, a boot management system of amobile communication terminal which may prevent a fatal error caused bydamage of a file header in an EFS area of the mobile communicationterminal, a method of updating a file in the mobile communicationterminal, and a method of booting the mobile communication terminalwhich may prevent a fatal error caused by damage of a file header in anEFS area of the mobile communication terminal.

According to an embodiment of the present invention, there is provided afile update system of a mobile communication terminal, including: a filereader reading a file to be updated from an EFS area of the mobilecommunication terminal; an EFS area assignment unit assigning an EFSarea for storing an updated file; and an update processor storing anupdated file in the EFS area assigned by the EFS area assignment unit,reading old version information from a header of the file to be updated,and recording newer version information than the old version informationin a header of the updated file.

According to another embodiment of the present invention, there isprovided a boot management system of a mobile communication terminal,when a file name is damaged in a header of a file stored in an EFS areaso that there are at least two files having the same ID in the EFS area,the boot management system which reads a header of a file of a versionpreceding to a version of the damaged file, registers the read header inan EFS area table, and boots the mobile communication terminal so that afatal error caused by damage of the header of the file in the EFS areacan be prevented from occurring.

The boot management system may include: a header reader reading a headerof a file registered in an EFS area table; an error processor, when afile name is damaged in a header of a file registered in the EFS areatable, analyzing header information of files stored in the EFS area,retrieving file names of files having the same ID as that of the damagedfile, and recording header information of a file of a newest versionamong the files having the same ID in the EFS area table, therebyrecovering the EFS area table; and a boot processor performing a processof initializing the EFS area table using the EFS area table recovered bythe error processor.

According to still another embodiment of the present invention, there isprovided a mobile communication terminal equipped with the file updatesystem.

According to a further embodiment of the present invention, there isprovided a mobile communication terminal equipped with the bootmanagement system.

According to another embodiment of the present invention, there isprovided a method of updating a file in a mobile communication terminal,the method including the operations of: reading a file to be updatedfrom an EFS area of the mobile communication terminal; assigning an EFSarea for storing an updated file; and storing an updated file in the EFSarea assigned in the operation of assigning an EFS area, reading oldversion information from a header of the file to be updated, andrecording newer version information than the old version information ina header of the updated file.

According to another embodiment of the present invention, there isprovided a method of booting a mobile communication terminal, the methodincluding the operations of: reading a header of a file registered in anEFS area table; if a file name is damaged in the header of the fileregistered in the EFS area table, analyzing header information of filesstored in an EFS area, retrieving file names of files having the same IDas that of the damaged file, and recording header information of a fileof a newest version among the files having the same ID in the EFS areatable, thereby recovering the EFS area table; and performing a processof initializing the EFS area table using the recovered EFS area table.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other features and advantages of the present inventionwill become more apparent by describing in detail exemplary embodimentsthereof with reference to the attached drawings in which:

FIG. 1 is a flash memory structure of a mobile communication terminal inaccordance with an embodiment of the present invention;

FIG. 2 is a block diagram of a file update system of a mobilecommunication terminal in accordance with an embodiment of the presentinvention;

FIG. 3 is a block diagram of a boot management system of a mobilecommunication terminal in accordance with another embodiment of thepresent invention, which is capable of preventing a fatal error causedby damage of a file header in an EFS area of the mobile communicationterminal;

FIG. 4 is a flow chart of a method of updating a file in a mobilecommunication terminal in accordance with still another embodiment ofthe present invention; and

FIG. 5 is a flow chart of a method of booting a mobile communicationterminal in accordance with a further embodiment of the presentinvention, which is capable of preventing a fatal error caused by damageof a file header in an EFS area of the mobile communication terminal.

DETAILED DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

Exemplary embodiments in accordance with the present invention will nowbe described in detail with reference to the accompanying drawings.

FIG. 1 is a flash memory structure of a mobile communication terminal inaccordance with an embodiment of the present invention. A flash memoryof a mobile communication terminal includes a code area for storing anoperating system (OS) and core applications, which are essential inoperating the mobile communication terminal, and an embedded file system(EFS) area for storing short messages, pictures, bell sounds, or games.

The code area of the flash memory of the mobile communication terminalsupporting NAND booting typically includes an area for storing a bootloader which is first run to boot the mobile communication terminal uponpower-on of the mobile communication terminal, a boot information block(BIB) for storing information referenced by the boot loader, and afirmware area for storing the OS and core applications in a binary form.

A file update system 100 of a mobile communication terminal according tothe embodiments of the present invention exists in a software form. Thefile update system 100 reads a file (file 1) to be updated from an EFSarea, assigns an EFS area to store an updated file (file 2) therein, andstores the updated file (file 2) in the assigned EFS area. At this time,the file update system 100 reads old version information from a header(not shown) of the to-be-updated file (file 1), and records newerversion information than the old version information on a header (notshown) of the updated file (file 2).

A boot management system 200 of a mobile communication terminal whichprevents a fatal error from occurring due to damage of a header of anEFS area exists in a boot loader program run in the mobile communicationterminal. The boot management system 200 reads a header (not shown) of afile registered in an EFS area table contained in the BIB of the codearea. If a file name is damaged in the header of the file registered inthe EFS area table, the boot management system 200 analyzes headerinformation of files stored in the EFS area, and retrieves files havingthe same ID as that of the file whose file name is damaged. The bootmanagement system 200 records header information of the newest versionamong the files having the same ID in the EFS area table, therebyrecovering the EFS area table.

FIG. 2 is a block diagram of a file update system of a mobilecommunication terminal according to an embodiment of the presentinvention.

The file update system 100 includes a file reader 110, an EFS areaassignment unit 120, and an update processor 130. The file reader 110reads a file to be updated from an EFS area of the mobile communicationterminal.

To update a file stored in the EFS area of the mobile communicationterminal, the file update system 100 reads a file to be updated from theEFS area of the mobile communication terminal by means of the filereader 110. The EFS area assignment unit 120 assigns an EFS area tostore an updated file.

If the file read from the file reader 110 is updated, the updated file(file 2) is stored in an EFS area different from an EFS area in whichthe file prior to updating is stored. The file update system 100 assignsan EFS area to store the updated file by means of the EFS areaassignment unit 120. Memory assignment technologies are well known inthe art and a detailed description thereof will thus be omitted herein.

The update processor 130 stores the updated file read from the filereader 110 in the EFS area assigned by the EFS area assignment unit 120,reads old version information from a header of the to-be-updated file,and records newer version information than the old version informationin a header of the updated file.

That is, when the header of the updated file is damaged, the file updatesystem 100 records newer version information than old versioninformation in the header of the updated file by means of the updateprocessor 130 and stores the updated file in the assigned EFS area sothat Same Owner ID Error occurred due to the damaged header cannot causethe mobile communication terminal to be automatically power-reset.

Meanwhile, since the version information is recorded in a header of afile stored in the EFS area, when the Same Owner ID Error occurs due toa damaged header, a boot management system 200 of the mobilecommunication terminal, which prevents a fatal error caused by thedamaged header of the EFS area, recovers the Same Owner ID Error usingthe file prior to updating.

FIG. 3 is a block diagram of a boot management system of a mobilecommunication terminal preventing a fatal error caused by damage of aheader of an EFS area in accordance with an embodiment of the presentinvention.

As shown in FIG. 3, when a file name is damaged in a header of a filestored in an EFS area so that there are at least two files having thesame ID, a boot management system 200 of a mobile communication terminalaccording to an embodiment of the present invention reads a header of afile of a version preceding to a version of the damaged file andregisters it in an EFS area table so that a fatal error caused by thedamage of the header of the EFS area can be prevented from occurring.

The boot management system 200 includes a header reader 210, an errorprocessor 220, and a boot processor 230. The header reader 210 reads aheader of a file registered on an EFS area table.

When the mobile communication terminal is powered on, the bootmanagement system 200, which prevents a fatal error caused by damage ofa header of an EFS area, performs a process of booting the mobilecommunication terminal.

The boot management system 200 performs a process of initializing theEFS area table during the booting process. That is, the boot managementsystem 200 reads a header of a file registered on the EFS area table bymeans of the header reader 210 by making reference to the EFS area tablecontained in a BIB of a code area.

When a file name is damaged in a header of a file registered on the EFSarea table, the error processor 220 analyzes header information of filesstored in the EFS area, retrieve file names of files having the same IDas that of the damaged file, and records header information of a newestversion among the files having the same ID in the EFS area table,thereby recovering the EFS area table.

If a header of the file registered on the EFS area table is not damaged,the boot management system 200 performs a typical process ofinitializing the EFS area table using a file of a newest version bymeans of the boot processor 230.

However, if a file name is damaged in a header of a file registered onthe EFS area table, the error processor 220 of the boot managementsystem 200 analyzes header information of files stored in the EFS area,retrieves file names of files having the same ID as that of the damagedfile, and records header information of a file of a newest version amongthe files having the same ID in the EFS area table, thereby recoveringthe EFS area table.

The boot processor 230 performs a process of initializing the EFS areatable using the EFS area table recovered by the error processor 220.

That is, if a header of a file recognized in the EFS area table is notdamaged, the boot management system 200 performs a process ofinitializing the EFS area table using a file of a newest version bymeans of the boot processor 230.

However, if a file name is damaged in a header of a file registered onthe EFS area table, the boot management system 200 performs a process ofinitializing the EFS area table using the EFS area table recovered bythe error processor 220.

Accordingly, the embodiments may efficiently recover Same Owner ID Errorcaused by damage of a file header in the EFS area.

FIG. 4 is a flow chart of a method of updating a file of a mobilecommunication terminal in accordance with an embodiment of the presentinvention.

In operation S110, the file update system 100 reads a file to be updatedfrom an EFS area of the mobile communication terminal.

In operation S120, the file update system 100 assigns an EFS area tostore an updated file.

In operation S130, the file update system 100 stores an updated file inthe EFS area assigned in operation S120, reads old version informationfrom a header of the to-be-updated file, and records newer versioninformation than the old version information in the header of theupdated file.

FIG. 5 is a flow chart a method of booting a mobile communicationterminal preventing a fatal error caused by damage in a header of an EFSarea in accordance with an embodiment of the present invention.

In operation S210, the boot management system 200 reads a header of afile registered on an EFS area table contained in a BIB of a code area.

In operation S220, if a file name is damaged in the header of the fileregistered on the EFS area table, the boot management system 200analyzes header information of files stored in the EFS area, retrievesfile names of files having the same ID as that of the damaged file, andrecords header information of a file of a newest version among the fileshaving the same ID in the EFS area table, thereby recovering the EFSarea table.

In operation S230, the boot management system 200 performs a typicalprocess of initializing the EFS area table using the EFS area tablerecovered in operation S220, thereby recovering Same Owner ID Errorcaused by damage of the header of the file in the EFS area.

As apparent from the above description, according to the embodiments ofthe present invention, it may be possible to recover the Same Owner IDError caused by damage of a header of a file in an EFS area of a mobilecommunication terminal.

While the present invention has been described with reference toexemplary embodiments thereof, it will be understood by those skilled inthe art that various changes in form and details may be made thereinwithout departing from the scope of the present invention as defined bythe following claims and their equivalents.

What is claimed is:
 1. A mobile communication terminal, comprising: anembedded file system (EFS) area comprising a header of a filecorresponding to a first version; and a processor, wherein, if theheader of the file corresponding to the first version and stored in theembedded file system (EFS) area is damaged, the processor reads a headerof a same file corresponding to a version preceding the first version,and registers the read header in an EFS area table for boot management.2. The mobile communication terminal of claim 1, comprising: a headerreader to read information of the file registered in the EFS area table,wherein the processor, if a file name is damaged in the damaged headerof the file, analyzes header information of files stored in the EFS areato retrieve file names of files having identification (ID) correspondingto ID of the file having the damaged header and to identify the headerof the file corresponding to the version preceding the first version. 3.The mobile communication terminal of claim 1, wherein the processorreboots and initializes the EFS area table after registering the readheader.
 4. The mobile communication terminal of claim 1, wherein, duringan initialization process of the EFS area table, the processordetermines whether the header of the file stored in the EFS area isdamaged.
 5. A method of booting a mobile communication terminal, themethod comprising: reading a header of a file registered in an embeddedfile system (EFS) area table; if a file name is damaged in the header ofthe file registered in the EFS area table, analyzing header informationof files stored in an EFS area, retrieving file names of files havingthe same identification (ID) as the damaged file, and recording headerinformation of a file of a newest version among the files having thesame ID in the EFS area table to recover the EFS area table; andinitializing the EFS area table using the recovered EFS area table.
 6. Amethod of booting a mobile communication terminal, the methodcomprising: reading header information of a first file registered in anembedded file system (EFS) area table; determining whether a header ofthe first file is damaged; in response to a determination that theheader of the first file is damaged, retrieving header information of asecond file, the second file being a version of the first file differentfrom the damaged version of the first file, the first file and thesecond file having a same file identification (ID); and registering theretrieved header information of the second file into the EFS area table.7. The method of claim 6, wherein a Boot Information Block (BIB)comprises the embedded file system (EFS) area table.
 8. The method ofclaim 6, wherein the reading of the header information of the first filefrom the EFS area table is performed during a boot process.
 9. Themethod of claim 6, further comprising: determining whether to search forone or more files having the file identification if the header of thefirst file is damaged or an error occurs with respect to the first file.10. The method of claim 6, further comprising: rebooting the mobilecommunication terminal if the retrieved header information of the secondfile is registered into the EFS area table.
 11. A mobile communicationterminal, comprising: a memory comprising an embedded file system (EFS)area table; and a processor to read header information of a first fileregistered in the EFS area table, and to determine whether a header ofthe first file is damaged, wherein, in response to a determination thatthe header of the first file is damaged, the processor is configured toretrieve header information of a second file corresponding to a versionof the first file different from the damaged version of the first file,the first file and the second file having a same file identification(ID), and to register the retrieved header information of the secondfile into the EFS area table.
 12. The mobile communication terminal ofclaim 11, wherein a Boot information Block (BIB) of the memory comprisesthe embedded file system (EFS) area table.
 13. The mobile communicationterminal of claim 11, wherein the header information of the first fileis read from the EFS area table during a boot process.
 14. The mobilecommunication terminal of claim 11, wherein the processor is configuredto determine whether to search for one or more files having the fileidentification if the header of the first file is damaged or an erroroccurs with respect to the first file.
 15. The mobile communicationterminal of claim 11, wherein the processor is configured to reboot themobile communication terminal if the retrieved header information of thesecond file is registered into the EFS area table.